MM - Monitor Method
-------------------

This transaction is used to specify the method of sample collection and analysis (the sampling methodology) of the monitor for specified date ranges. Only 1 method can be specified at any given time, and only one method per day can be specified (that is, methods cannot be changed on an hourly basis). 

This information used to be defined ny what was submitted on the Raw Data (RD) transaction and is now defined as a property of the monitor.  If an RD transaction is submitted with a different method than indicated on this record, the data will be rejected with an error message.

"Method Switching" between samples - if necessary for filters - should not be done; rather, two monitors (POCs) should be established, per the technical note at: https://www.epa.gov/sites/production/files/2017-02/documents/20130618technicalnotepoc.pdf


Rules
^^^^^

All days of operation for a criteria monitor must be covered by a FEM or FRM method unless exclusion has been requested.


Examples:

.. code-block:: text
   :caption: MM transaction in default mode

   MM|I|06|001|0012|88101|3|170|20140201|

.. code-block:: text
   :caption: MM transaction in Tribal mode

   MM|I|TT|434|0007|11101|1|091|20020607|


Format
^^^^^^

.. list-table:: MM - Monitor Method transaction format
   :widths: 1 5 15 4 3 1
   :header-rows: 1


   * - Seq.
     - Name
     - Description
     - Formatting Rules
     - Required
     - Key
   * - 1
     - `Transaction Type <Transaction%20Type.html>`_
     - Monitor Method transaction identifier.
     - Must = MM
     - Always
     - 
   * - 2
     - `Action Indicator <Action%20Indicator%20for%20Transaction.html>`_
     - Indicator for Insert, Update, or Delete action.
     - Must = I, U, or D
     - Always
     - 
   * - 3
     - `State Code / Tribal Indicator <State%20Code.html>`_
     - The FIPS state code of the monitor, or "TT" to indicate that the next field on the transaction is a Tribal code.
     - Must exist in STATES Reference Table or be 'TT' for Tribal Site
     - Always
     - Y
   * - 4
     - `County Code / Tribal Code <County%20Code.html>`_
     - The FIPS County Code of the site.  If the previous field on the transaction contains "TT", then the Tribal Code of the site.
     - Must exist in COUNTIES (for state) or TRIBAL_AREAS Reference table
     - Always
     - Y
   * - 5
     - `Site Number <Site%20Number.html>`_
     - Four digit number to uniquely identify site in county and/or tribe.
     - Must exist in SITES table with {State Code, county Code} or Tribal Code
     - Always
     - Y
   * - 6
     - `Parameter Code <Parameter%20Code.html>`_
     - The AQS parameter code assigned to the monitor in AQS.
     - Must exist in PARAMETERS reference table.
     - Always
     - Y
   * - 7
     - `POC <POC.html>`_
     - Parameter Occurrence Code:  One or two digit number identifying a specific monitor for a parameter at the site.  
     - Must exist in MONITOR table for non-Insert actions.
     - Always
     - Y
   * - 8
     - `Method Code <Method%20Code.html>`_
     - The sampling methodology (i.e. method of collection and analysis) implemented by monitor.
     - Must exist in SAMPLING METHODOLOGIES Reference table
     - Always
     - Y
   * - 9
     - `Begin Date <Begin%20Date.html>`_
     - Beginning of date range where the monitor implements the specified method.
     - YYYYMMDD.
     - Always
     - Y
   * - 10
     - `End Date <End%20Date.html>`_
     - End of date range where the monitor implements the specified method.
     - YYYYMMDD.
     - No
     -